"melo" <mel### [at] coxnet> wrote:
I had tried the new, easier syntax you recommended
 ppFigure()

I got a Parser error, complaining about expecting 5 parameters, and only finding
0.

Your working version sounds different than the downloadable version of PP.

Thanks,

Meltem

Is there any way to define transformation constraints in POV-RAY?  I need to
keep my skeletal objects forward feet locked in place whereever it lands, as he
brings his back leg forward into his cross-over pose ready to take his next
stride.

Another place where I might need transformation constraints is obstacle
avoidance, or not allowing him stepping into or thru hard objects.  Now he
steps into the floor or walks right thru the walls, he is very entertaining, as
he is.

Thanks again.   Of course, none of the above had been doable, since I left it to
POV-RAY to come up with coordinates of bone-segments & joints in my moved
(=posed) skeleton.

How I wish POV-RAY had allowed some kind of structure and linked list
definitions, how I wish it had known and informed its users about states.
It is obviously doing a whole bunch of marvelous, mathematically sound
computations, to be able to render complex CSG objects transformed in any
conciveable ways.

Well, this is the second time I am attempting to respond to this posting, the
first one has disappeared on me.  If they both appear, please accept my
appologies.

Cheers,
Meltem



> "Chris B" <nom### [at] nomailcom> wrote:
> > "melo" <mel### [at] coxnet> wrote in message
> > news:web.47d49e814b35a0df587ef5e20@news.povray.org...
> > > Hello, Chris,
> > >
> > > I have struggled some more with my animation, then started playing with
> > > POVPerson.  I was going to follow
> > > Quick reference step by step before I play with animation
> > >
> > > However I had not managed to go far:
> > >
> > > The online documentation recommends
> > >
> > > #include "povperson.inc"
> > >
> > > object
> > > {ppFigure("ann.inc","style1.inc","smile","standing.inc","ppoutfit1.inc")
> > > translate x*5}
> > >
> >
> > Ah yes. That is wrong. The example files like 'pp00example05.pov' contain
> > the later version of the syntax for the ppFigure macro, where all of the
> > parameters have been removed and where you need to 'include' files and call
> > macros to set specific options before calling the 'ppFigure' macro. This
> > allows defaults to be used and the parameters in the example above are
> > roughly the defaults.
> >
> > The minimum required to add a figure is therefore:
> >
> > #include "povperson.inc"
> > ppFigure()
> >
>
> Thanks Chris.  I will give this a whirl.  In the meantime.  I will still try to
> get the stick-figure Humanoid of my 1st try walk.  After all i had already
> invested 5-6 months in it. Ickkk!
>
> Who knows, there might be a way to export the current posed state of a skeletal
> object to Moray or Bishop from which one can interactively generate coordinates
> of next pose?
>
> Always the dreamer.
>
> Cheers,
> Meltem
>
> > Which adds an 'ann'  figure about 1.6 POV-Ray units tall standing at the
> > origin facing towards +Z. The hair looks terrible in this default figure as
> > it's cut to about 30 hairs to minimise the performance impact, so you may
> > want to try:
> >
> > #include "povperson.inc"
> > #include "ppstyle6.inc"
> > ppAddPoseFile("ppsitting.inc");
> > object {ppFigure() rotate y*180}
> > light_source { < 2, 60  ,-30> color rgb<1, 1  , 1  >*0.6 }
> > light_source { < 0, 24  ,-26> color rgb<1, 1  , 1  >*1.2 }
> > light_source { <5,  6.5,-10> color rgb<1, 0.5, 0.5>}
> > camera {
> >   location <-0.3, 1.08,-2.1>
> >   look_at  y
> > }
> >
> > which gives you a model with hair and a non-default pose.
> >
> > I do have an updated version of the users guide that I never got round to
> > publishing. I'll dig it out and see if it makes sense to replace the one
> > that's there.
> >
> > Regards,
> > Chris B.

Post a reply to this message